-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: esbuild plugin config logic #12493
Conversation
Run & review this pull request in StackBlitz Codeflow. |
delete resolvedOptions.include | ||
delete resolvedOptions.exclude | ||
delete resolvedOptions.jsxInject |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These were needed because there is a cast here: https://github.com/vitejs/vite/pull/12493/files#diff-6d149ac9706cd508b52db0c059a0f01d670620a9a5a73cd7b122ce62b6b69471R205, from our own extended options. These fields are no longer present when calling transformWithEsbuild
after the changes in this PR.
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
@sapphi-red here is the run against the merged commit: https://github.com/vitejs/vite-ecosystem-ci/actions/runs/4481055968 |
Description
Simplify the config logic of the
vite:esbuild
. It should also be a bit more performant, but it is too small to mark this as a perf PR. Avoiding changing the shape of the config throughdelete
s could help though.What is the purpose of this pull request?